Context: a mock paper is data, not a verdict
A Year 11 student finishes a GCSE maths mock with 58% and files it under ‘done’. The paper contains 42 marks lost, but the student remembers only the final score. duffspin changes the first move: before any new topic is revised, the paper is reviewed for causes. The review takes 20 minutes and uses a pen, a highlighter and the original question paper.
The raw score matters less than the pattern behind it. A student who lost six marks to misread questions and four to fraction arithmetic has a different revision week from one who lost marks to timing. duffspin makes that difference visible before the next practice paper.
Development: the four-bucket duffspin sort
Each lost mark is assigned to one of four buckets. The labels are deliberately plain so a student can use them without a tutor in the room. The aim is not a beautiful error log; it is a short list of causes that can be drilled.
- Misread question. The student underlined the wrong instruction or missed a unit. Example: giving the area when the question asked for the perimeter.
- Method gap. The student could not start the question or chose the wrong rule. Example: using the sine rule where right-angle trigonometry was needed.
- Arithmetic slip. The method was sound, but a sign, decimal or times-table error changed the answer.
- Timing panic. The student left the question blank or rushed the last page because the clock ran out.
The duffspin routine works best when the student says the cause aloud and the tutor checks only the label, not the answer. That keeps the review fast and stops it turning into a full lesson.
The limit: keep the review under 20 minutes
A duffspin review that runs for an hour becomes a retest, not a diagnosis. Set a timer, review only the questions that lost marks, and stop when each error has a bucket label. If a cause appears more than three times, that is the week’s priority. This keeps the review concrete and prevents it from replacing actual practice.
Result: a weekly drill plan with one target per cause
The review ends with no more than three drills for the week. Each drill is tied to a cause, not a topic, so the student practises the weak move in a fresh context. A method gap becomes two worked examples and five solo questions; an arithmetic slip becomes a 10-question mental warm-up; a timing issue becomes a timed 15-minute section.
- Monday: 10 minutes on arithmetic slips using five mixed questions, checked immediately.
- Wednesday: 15 minutes on method gaps using two new exam questions from the same strand.
- Friday: 15 minutes on timing using one exam section with a visible countdown.
After 72 hours, the student re-attempts three original questions from the mock without notes. Success is not a higher overall score; it is fewer repeat errors in the same bucket. That small shift is the point of duffspin: the next mock paper starts with a plan already attached.